SLock would still check for changes in the system clock being set back past the creation date of the component, even after the component was registered. This has been changed so that this no longer happens. SLock will now no longer check the system clock once the application has received a valid registration code
SLock now has the ability to store keys in the registry under Roots other than the default HKEY_CURRENT_USER. Two additional properties have been added to allow the programmer to control this: "RegKeyMainRoot" and "RegKeyBackRoot".
All existing applications will have to be undergo very minor changes to continue to function. For backwards compatibilty, the roots should be set to "CURRENT_USER" and will then access the existing registry keys for applications which have already been deployed. New applications can use the extended functionality.
SLock would report that the first start was sucessuful on the first start even if the DLL could not be found. Subsequent starts would correctly report that the registry info was damaged.
All existing applications will continue to function without change.
In ptDaysUsed mode the internal value of the Expiry date was not initialised (because it is not used in this mode) but validated. This caused a false report of a 'first start' on each start. The variable is now initialised in this mode
All existing applications will continue to function without change.
SLock has a new registration mode added which allows a simplified method of registration based only on the user name. This is intended for cheap applications where the level of security required is low and volume of sales are high.
An extra machine option has been added (moExtensions) which means that by setting all machine options to false, the only information required from the user to create an unlock code is his user name. All other settings are known to the program author.
All existing applications will continue to function without change.
The keys used by SLock in the registry were always the same. These have been changed into variable keys to make detection of an SLock protected application more difficult. You can now set both the KeyPath and the KeyName. The Properties 'RegKeyMain' and 'RegKeyBack' have been split into 'RegKeyMainPath' and 'RegKeyMainKey', 'RegKeyBackPath' and 'RegKeyBackKey' respectively.
The Property 'Status' is now set before calling the appropriate event. The order was originally to call the event and then set the property, which makes no sense.
In addition to the existing storage locations of the registration information, a third location has been added to make it very much more difficult to bypass SLock security. A third copy of the registration information can now be stored in a DLL file which can either be located in the Windows directory, or at another given location.
The property DLLName allows you to specify the location of the DLL. If this is given without a path, the DLL will be searched for in the Windows directory.
An additional property has been added to allow more flexibility in using the three locations of registration information. 'ProtectionOpt' allows you to set if the Backup registry location and or the DLL should be used to store the registration information. The Main registry location is always used.
In certain countries (e.g. Germany) the definition of Shareware is that the program should be used for a number of distinctive days - any day on which the software is not used should not be taken from the trial period.
SLock was not able to support this mode of operation, but has now been extended to have an additional protection mode 'ptDaysUsed'. In this mode SLock can be used for the given number of days, and any day on which SLock is not used will not be counted in this period.
